The help output names the three documents an operator is owed - #172
Closed
iderex wants to merge 1 commit into
Closed
The help output names the three documents an operator is owed#172iderex wants to merge 1 commit into
iderex wants to merge 1 commit into
Conversation
An operator who runs the binary and never opens the repository had no route to the intended-use notice, the licence or the privacy document. The runner knew where all three were and said nothing about any of them, so for that reader the three files did not exist. The last paragraph of the usage text now names them. It names rather than restates, because a paraphrase printed by a binary somebody downloaded months ago is a copy of a document that has since moved on and the reader cannot tell which of the two they hold. The two limits this rests on are written at the declaration rather than only in the issue. A notice is not a control and printing it prevents nothing, so it should not be counted as a thing that stops misuse when somebody later asks what does. And a notice an operator has to run a verb to see is weaker than one sitting in the download beside the binary, which is why both routes are wanted rather than either alone. The guard is here because nothing else in the tree holds these strings. The paths leg of the invariants scan takes this repository's own documents as its subject, which is the files at the root and everything under docs/, and a path named inside the runner is outside that by the leg's own reckoning. The test asserts both halves of the walk an operator makes: that the text names the file, and that the file is in the tree to be found. Part of #36. It closes neither clause of that done-condition, which asks for the version output and the release archive as well, and both of those wait on something that does not exist yet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded by #173 and closed unmerged. The change itself is unchanged and
lands there.
This branch carried no DCO sign-off, and the sign-off gate refused it by name:
The repair is a rebuild rather than a rewrite. I did not force-push this branch
and I have left it alone. The commit was rebuilt on a fresh branch with the
sign-off, and the two are proven to carry identical content rather than assumed
to:
Everything this pull request said about the change, the evidence behind it and
what it does not close is carried in the body of #173.